Method, apparatus and computer program product for integrating heterogeneous systems

ABSTRACT

Disclosed are a method, computer program product and apparatus for integrating resource and coordinator components in a heterogeneous computer system. The technique disclosed involves the introduction of a negotiation phase into the resource enlistment or registration process wherein the resource component and coordinator component request and respond with indicators showing the quality of service that each supports, thus jointly establishing at runtime a quality of service to be supported for the resource and coordinator pairing. The qualities of service may include commit phase support and recovery support.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 09/683,902 filed on Feb. 28, 2002 now U.S. Pat. No.7,389,350, the contents of which are hereby incorporated by reference inits entirety.

BACKGROUND OF INVENTION

1. Field of the Invention

This invention relates to the field of integration of enterpriseapplications and systems, and more particularly to the integration ofheterogeneous systems in which support for qualities of service, such assynchronization and recovery, may be required by some subsystems, andprovided or not provided by other subsystems.

2. Background of the Invention

Enterprise Application Integration (EAI) is key to many companies”business strategies. The ability to integrate existing systems with newsystems is seen as an essential in, for example, web-enabling existingapplications. A fundamental part of EAI is the ability to coordinateupdates made to disparate systems that form part of an enterpriseinformation system. For example, a new application, running on anapplication server, which brings together in an enterprise informationsystem two existing database applications and an Enterprise ResourcePlanning, or ERP, system (for example, SAP R/3) needs to be able tocoordinate updates made to those three systems. The inability to do socould result in loss of data integrity.

The technology, which provides the access to the systems and theintegration with the application server, is often referred to asConnectors. Connector coordination can be provided through twointerfaces, the coordinator and the resource. Resources can representEnterprise Information Systems, as shown in FIG. 2. An EnterpriseInformation System may comprise databases, ERP systems, and the like.The Resources require certain Quality of Service commitments from theirenvironments (via the Coordinator). (“Quality of Service” is used hereto refer to such characteristics of systems as their level of supportfor recoverability of data after a system failure. Some systems providefull recovery support, while others do not. Other such characteristicsare, for example, the ability or otherwise to support asynchronousprocessing.) The use of coordinator and resource interfaces is found intransaction services such as that provided by the Object ManagementGroup's (OMG) CORBA specification, known as the Object TransactionService (OTS). In general with such services, the implementation of boththe resource and the coordinator is provided by the same organization.This means that the Quality of Service (QOS) required and provided byeach is known from the beginning.

EAI introduces a new dimension of difficulty which is unavoidable due tothe large numbers of heterogeneous systems which need to be integrated,and the large number of application servers which need to provideintegration. A significant problem is that the implementers of thecoordinator or coordinators and the implementers of the resource orresources may be different organizations whose members may never havemet or communicated. In an attempt to overcome the differences betweensystems supplied by different vendors, the J2EE Connector Architecturespecification allows a resource adapter to describe a resource'scapabilities in a deployment descriptor, but the application server andthe coordinator are required to support all possible options, which iscumbersome for some lightweight runtimes.

Measures of QOS for coordinators and resources include commit phasesupport (also known as sync level support), which may be one phasecommit or two phase commit, and recovery support (that is, whether ornot logging is supported to preserve integrity beyond a system crash).

The ways in which these QOS are provided, and the QOS resulting fromdifferent coordinator and resource pairings can vary greatly, and somepairings may be invalid. The provision of commit phase support andrecovery support is essential in systems which have a characteristicknown as “transactionality”.

The term “transactionality” is used in the field of data processing torefer to the characteristic of a piece of data processing work that maybe defined as having a necessary unity. For example, the data processingtask of processing a cash withdrawal from an automated teller machinehas several elements, but all must take place for the transaction to becompleted. The user's identity must be verified, the cash must beissued, and the user's account must be updated to reflect the newbalance after the withdrawal, and so on. If the machine runs out of cashor suffers some other failure, so that the withdrawal does not takeplace, the user's account must not be updated, or, if it has alreadybeen updated before the point of failure, the update must be cancelledso that the account returns to its previous state. For backgroundinformation on the properties of transactions, see TransactionProcessing: Concepts and Techniques, J. Gray and A. Reuter.

Clearly, however, there exist more complex business environmentsrequiring characteristics other than those of this simple, unitarytransaction model, and these are the subject of continuing study andresearch. For background information on more complex transactionenvironments, see Database Transaction Models, Ahmed K. Elmagarmid, ed.,and Advanced Transaction Models and Architectures, jajodia andKerschberg, eds. Examples taken from real life include, for example, thebooking of a vacation, which may involve multiple transactions to bookflights and hire cars, reserve hotel rooms, and so on, using a number ofdifferent systems independently developed by different suppliers. Themanagement of transactions and coordination of updates in suchenvironments adds to the complexity of the problems faced by applicationdevelopers, and the cumbersome nature of existing solutions isunacceptable in environments in which performance is critical.

SUMMARY OF INVENTION

The present invention accordingly provides, in a first aspect, a methodfor integrating heterogeneous processing systems, the method comprisingthe steps of:

requesting by a first one of a resource component and coordinator pair afirst indicator indicating a first quality of service supported by asecond one of the pair; responding by the second one of the pair withthe first indicator; receiving by the first one of the pair the firstindicator; responsive to the first indicator, determining by the firstone of the pair whether the first quality of service is acceptable;responsive to the determining, offering by the first one of the pair topermit one of joining in coordination with the second one of the pairand not joining in coordination with the second of the pair; responsiveto the offering by the first one of the pair to permit joining incoordination with the second one of the pair, requesting by the secondone of the pair a second indicator indicating a second quality ofservice acceptable to the first one of the pair; responding by the firstone of the pair with the second indicator; receiving by the second oneof the pair the second indicator; responsive to the second indicator,determining by the second one of the pair to permit joining incoordination with the first one of the pair; and responsive todetermining by the second one of the pair to permit joining incoordination with the first one of the pair, determining a quality ofservice provision for the coordination.

In a second aspect, the present invention provides a computer programproduct comprising computer program code tangibly embodied in a signalbearing medium, the computer program code comprising instructions to,when loaded into a computer system and executed, cause the computer toperform the steps of: requesting by a first one of a resource componentand coordinator pair a first indicator indicating a first quality ofservice supported by a second one of the pair; responding by the secondone of the pair with the first indicator; receiving by the first one ofthe pair the first indicator; responsive to the first indicator,determining by the first one of the pair whether the first quality ofservice is acceptable; responsive to the determining, offering by thefirst one of the pair to permit one of joining in coordination with thesecond one of the pair and not joining in coordination with the secondof the pair; responsive to the offering by the first one of the pair topermit joining in coordination with the second one of the pair,requesting by the second one of the pair a second indicator indicating asecond quality of service acceptable to the first one of the pair;responding by the first one of the pair with the second indicator;receiving by the second one of the pair the second indicator; responsiveto the second indicator, determining by the second one of the pair topermit joining in coordination with the first one of the pair; andresponsive to determining by the second one of the pair to permitjoining in coordination with the first one of the pair, determining aquality of service provision for the coordination.

In a third aspect, the present invention provides apparatus forintegrating heterogeneous processing systems, the apparatus comprising:a first requester for requesting by a first one of a resource componentand coordinator pair a first indicator indicating a first quality ofservice supported by a second one of the pair; a first responder forresponding by the second one of the pair with the first indicator; areceiver for receiving by the first one of the pair the first indicator;a determining element being responsive to the first indicator, fordetermining by the first one of the pair whether the first quality ofservice is acceptable: an offering element being responsive to thedetermining, for offering by the first one of the pair to permit one ofjoining in coordination with the second one of the pair and not joiningin coordination with the second of the pair; a second requestor beingresponsive to the offering by the first one of the pair to permitjoining in coordination with the second one of the pair, for requestingby the second one of the pair a second indicator indicating a secondquality of service acceptable to the first one of the pair; a secondresponder for responding by the first one of the pair with the secondindicator; a second receiver for receiving by the second one of the pairthe second indicator; a second determining element being responsive tothe second indicator, for determining by the second one of the pair topermit joining in coordination with the first one of the pair; and athird determining element being responsive to determining by the secondone of the pair to permit joining in coordination with the first one ofthe pair, for determining a quality of service provision for thecoordination.

Various other objects, features, and attendant advantages of the presentinvention will become more fully appreciated as the same becomes betterunderstood when considered in conjunction with the accompanyingdrawings, in which like reference characters designate the same orsimilar parts throughout the several views.

BRIEF DESCRIPTION OF DRAWINGS

Preferred embodiments of the present invention will now be described byway of example only, with reference to the accompanying drawings.

FIG. 1 shows a computer system according to a preferred embodiment ofthe present invention.

FIG. 2 shows the architecture of the prior art as described in the J2EEConnector Architecture specification.

FIG. 3 shows the enlisting of a resource for it to participate in atransaction as defined in the prior art J2EE specification.

FIG. 4 shows an augmentation of the J2EE enlistment process according toa first preferred embodiment of the present invention.

FIG. 5 shows how a resource becomes registered with a coordinator asdefined by the prior art CORBA Object Transaction Service (OTS).

FIG. 6 shows an augmentation of the OTS resource registering processaccording to a second preferred embodiment of the present invention.

DETAILED DESCRIPTION

Preferably, said first one of said pair comprises a resource componentand said second one of said pair comprises a coordinator.

Preferably, said resource component comprises a resource manager.

Preferably, said resource component comprises a resource adapter.

Preferably, a resource manager of the first aspect comprises a databasemanager.

Preferably, said resource manager comprises an Enterprise ResourcePlanning system.

Preferably, said coordinator comprises a transaction manager.

Preferably, said first one of said pair comprises a coordinator and saidsecond one of said pair comprises a resource component.

Preferably, said resource component comprises a resource manager.

Preferably, said resource component comprises a resource adapter.

Preferably, said resource manager comprises a database manager.

Preferably, said resource manager comprises an Enterprise ResourcePlanning system.

A method according to the first aspect may be performed at startup of aserver.

A method performed at the startup of a server preferably comprises theprior step of: sending, by said server, a request to a first one of aresource and coordinator pair to initiate requesting said firstindicator indicating a quality of service supported by a second one ofresource and coordinator pairs.

Preferably, at least one of said first and said second qualities ofservice comprises a commit phase support.

Further preferably, said commit phase support comprises at least one ofone phase commit support and two phase commit support.

Preferably, at least one of said first and said second qualities ofservice comprises recovery support.

Preferably, at least one of said resource component and coordinator paircomprises a platform-independent program code component.

Preferably, a quality of service provision is renegotiated.

Preferred features of the second aspect comprise program elements toperform steps corresponding to the preferred steps of the method of thefirst aspect.

Preferred features of the third aspect comprise means in the apparatusto perform actions corresponding to the preferred steps of the method ofthe first aspect.

The present invention thus provides for a negotiation phase between acoordinator and a resource. It does not mandate one particular way ofperforming this negotiation. One skilled in the art will clearly seethat there are a number of possible implementations, with the steps ofthe negotiation being carried out in sequences other than that describedin the preferred embodiment.

Advantageously, in the present invention neither the coordinator nor theresource has sole responsibility for determining whether a particularresource can be coordinated by a particular coordinator. The decision ismade by mutual agreement.

The use of a negotiation phase according to the present invention thusadvantageously allows more flexibility and the ability for thecoordinator and resource to agree on the Quality of Service the pairingcan provide, allowing for runtime environments in which not allqualities of service need to be allowed for, and thereby permitting theuse of smaller, less resource-consuming runtimes.

Preferred embodiments of the present invention may be implemented inapparatus as shown in FIG. 1, in which a computer system (100) comprisesa resource component (102) and a coordinator (104). Resource component(102) comprises a requester element (106) for requesting a QOS supportedindicator from the coordinator (104). Coordinator (104) comprises aresponder element (108) for responding with a QOS supported indicator.Resource component (102) further comprises a receiving element (110)which receives the QOS supported indicator, and a determining element(112) for determining whether or not the QOS indicator is such that theresource component (102) should offer to be coordinated by thecoordinator (104). Resource component (102) further comprises anoffering element (114) for offering to be coordinated by the coordinator(104). Coordinator (104) further comprises a requester element (116) forrequesting, in response to an offer, a QOS supported indicator fromresource component (102). Resource component (102) additionallycomprises a responder element (118) for responding with a QOS supportedindicator. Coordinator (104) comprises a receiver element (120) forreceiving a QOS supported indicator from resource component (102), and adetermining element (122) for determining whether or not the QOSsupported indicator is such that coordinator (104) should agree tocoordinate resource component (102). Finally, coordinator (104)comprises a determining element (124) for determining the QOS provisionthat is required to coordinate the resource component (102). In analternative embodiment, the elements and components shown in theresource component (102) and the elements and components in thecoordinator (104) may be arranged the other way round from that shown inthe exemplary drawing in FIG. 1, so that, for example, it is a requesterelement in the coordinator that initiates the exchange of flows, and theexchange of flows continues with a response from a responder element inthe resource component, and so on to the end of the negotiation.

It will be clear that the embodiment as shown in FIG. 1 is simplifiedfor ease of understanding, and that any combinations of computer systemsin networks may equally be used in implementing the resource andcoordinator components having the features of the preferred embodimentsof the present invention. Clearly, too, in such environments, various ofthe elements of the coordinators and resources may themselves bedistributed across multiple computer systems. It will also be clear thatthere are a number of possible implementations wherein the steps of thenegotiation are carried out in sequences other than that described inthe preferred embodiment. The negotiation steps of providing anindicator and requesting an indicator might, for example, be combined ina single message to reduce the number of flows across a network, and thenegotiation may be initiated by either the resource, the coordinator, ora “third party”.

In the preferred embodiments of the present invention, agreement betweena resource and a coordinator is achieved in a minimum of two stages:

1. The resource queries the coordinator for any relevant information itneeds in order to make its decision (coordinator QOS information). Forexample, if the resource supports two phase commit, and recovery, thenit queries the coordinator, through known methods on the coordinatorinterface, as to whether it supports two phase commit and recovery. Ituses the information it gets back to determine whether it will offeritself to the coordinator for coordination.

2. When the resource is offered to the coordinator, the Coordinatorqueries the resource to determine what level of support the resourceprovides (resource QOS information). The coordinator uses thisinformation to decide whether to allow the resource to be coordinated,and, if so, how. This decision can then be fed back to the applicationserver in the form of an information or warning message stating what QOSthe resource and coordinator pairing will provide.

Again, it will be readily apparent to one skilled in the art that thenegotiation between the resource and the coordinator may equally well becarried out the other way round.

A Quality of Service table can be used to represent the possiblecontracts for coordinator and resource pairings. These contracts arematched up to determine the resulting QOS at runtime. Below is anexample of a QOS table showing the resulting QOS achieved when matchingdifferent coordinator and resource QOS. The example shown is onlyintended to demonstrate such a table. Tables may differ depending onwhat assumptions are made. A “-” means that the value is irrelevant tothe resulting QOS. “Bracketing” means that the resources are told whento commit or rollback, but do not vote on the decision. “DistributedBracketing” means the resources are able to vote on the outcome, andtherefore the decision is distributed. “Atomic Transaction” means thatthere is no voting, but there is recovery. “Distributed AtomicTransaction” means that all the resources vote on the outcome, and canbe recovered.

Coordinator Resource Number of Quality of Phase Recovery Phase RecoveryResources Service 1 No — — 1 Bracketing — — 1 No 1 Bracketing — No 1 — 1Bracketing 1 — — No 1 Bracketing 1 — — — >1 Bracketing — — 1 — >1Bracketing 2 No 2 — — Distributed Bracketing 2 — 2 No — DistributedBracketing 1 Yes — Yes 1 Atomic Transaction — Yes 1 Yes 1 AtomicTransaction 2 Yes 2 Yes — Distributed Atomic Transaction

The following assumptions were made in the creation of this table:

1. A two phase capable resource or coordinator can use one phase whenthere is only one resource registered (OTS behaves in this way).

2. There is no Last Agent Optimization (this technique permits a singleone phase capable resource to be part of a distributed transaction).

3. A one phase capable resource can register with a two phase capablecoordinator and a two phase capable resource can register with a onephase capable coordinator.

It will be clear to one skilled in the art that these assumptions mayvary, depending on the nature of the heterogeneous systems that areparticipating in the overall data processing task.

In FIG. 2 is shown a typical configuration of elements comprising aprior art system as defined in the J2EE specification, in which atransaction contract exists between a transaction manager (whichrepresents one possible embodiment of a coordinator) and a resourceadapter.

The process by which a resource is enlisted in a system of the prior artdefined in the J2EE specification is shown in FIG. 3. At Step 1, anapplication server issues a getXAResource call to the managed connectionof the resource adapter. At Step 2, the application server issues aTransaction.enlistResource resource call to the transaction manager. AtStep 3, the transaction manager issues an XAResource.start call to theXAResource.

In a first preferred embodiment of the present invention, as shown inFIG. 4, an additional negotiation phase has been inserted between Steps2 and 3 of the enlistment process.

Steps 2.1-2.3 are the additional calls created for this negotiationphase. During the enlist, the transaction manager requests thecapabilities from the XAResource (the querycapabilities call). Thedetails of how the capabilities that are returned are specified is notpart of the subject matter of the present invention, but they mayimplement any interface which allows the resource to describe all itscapabilities, such as one or two phase commit, recovery, etc. Oneskilled in the art will readily understand that there may be variousdetailed implementations of such an interface, and that the capabilitieslisted above (commit support and recovery support) are given as examplesrather than being intended as an exhaustive list. The transactionmanager decides, based on the returned capabilities, whether it iscapable of coordinating the XAResource. If it is capable then itcontinues on to step 2.2. If not it returns a failure from theenlistResource call.

In step 2.2, the transaction manager offers itself to the XAResourcethus permitting the resource to communicate with the transactionmanager. In step 2.3, the XAResource queries the transaction manager'scapabilities. As with the capabilities of the XAResource, the details ofhow they are specified is not part of the subject matter of the presentinvention, but it may implement the same, or a similar, specifiedinterface which allows the transaction manager to describe all itscapabilities, such as one or two phase commit, recovery, etc. Again,these capabilities are intended as examples only, and one skilled in theart will readily perceive that information about other capabilities mayalso be included in the interface. The XAResource decides, based on thereturned capabilities, whether it believes it should be coordinated bythe transaction manager. If it is satisfied then it returns anacceptance from the offerTransactionManager (which may just be anon-error return). If not it returns a “rejection” from theoff-erTransactionManager call (which could be in the form of anexception). This rejection is then mapped to a failure from theenlistResource call. One skilled in the art will readily understand thatthe return messages may alternatively take the form of more detailedinformational messages, and that it is envisioned that furthernegotiation steps may be added where, for example, a “second-best-fit”might be acceptable to the resource and coordinator pair.

FIG. 5 shows the prior art process by which a resource is registeredwith a coordinator as defined in the OTS specification. In Step 1, aresource adapter issues a “new” call to a resource. In Step 2, theresource adapter issues “get_control”, and at Step 3, “get_coordinator”.The resource adapter is now in communication with the coordinator, andat Step 4, it issues “register-resource”.

In a second preferred embodiment of the present invention, shown in FIG.6, Steps 4.1-4.3 show an example of the additional calls required toimplement the negotiation technique in an OTS environment.

In both the first and the second preferred embodiments, the negotiationis performed between the resource and the coordinator (or transactionmanager). One will readily perceive that this negotiation could equallywell be performed between the resource adapter and the coordinator.However, this embodiment would require the specification of wholly newinterfaces rather than the augmentation of existing interfaces, and istherefore less preferred.

A further alternative embodiment of the present invention would be tohave the negotiation phase performed at server startup. In thisalternative embodiment, the server would initiate the negotiationbetween the transaction manager and all the deployed resources orresource adapters.

The present invention is preferably embodied as a computer programproduct for use with a computer system. Such an implementation maycomprise a series of computer readable instructions either fixed on atangible medium, such as a computer readable medium, e.g., diskette,CD-ROM, ROM, or hard disk, or transmittable to a computer system, via amodem or other interface device, over either a tangible medium,including but not limited to optical or analog communications lines, orintangibly using wireless techniques, including but not limited tomicrowave, infrared or other transmission techniques. The series ofcomputer readable instructions embodies all or part of the functionalitypreviously described herein.

It will be appreciated that such computer readable instructions can bewritten in a number of programming languages for use with many computerarchitectures or operating systems. Further, such instructions may bestored using any memory technology, present or future, including but notlimited to, semiconductor, magnetic, or optical, or transmitted usingany communications technology, present or future, including but notlimited to optical, infrared, or microwave. It is contemplated that sucha computer program product may be distributed as a removable medium withaccompanying printed or electronic documentation, e.g., shrink wrappedsoftware, pre-loaded with a computer system, e.g., on a system ROM orfixed disk, or distributed from a server or electronic bulletin boardover a network, e.g., the Internet or World Wide Web.

It is to be understood that the provided illustrative examples are by nomeans exhaustive of the many possible uses for my invention.

From the foregoing description, one skilled in the art can easilyascertain the essential characteristics of this invention and, withoutdeparting from the spirit and scope thereof, can make various changesand modifications of the invention to adapt it to various usages andconditions.

It is to be understood that the present invention is not limited to thesole embodiment described above, but encompasses any and all embodimentswithin the scope of the following claims:

1. A method comprising the steps of: utilizing a processor to integrateheterogeneous processing systems, wherein to integrate heterogeneousprocessing systems further comprises: requesting by a first one of aresource component and coordinator pair a first indicator indicating afirst quality of service supported by a second one of said pair, saidfirst one and said second one of said pair disposed within differentheterogeneous processing systems; responding by said second one of saidpair with said first indicator; receiving by said first one of said pairsaid first indicator; responsive to said first indicator, determining bysaid first one of said pair whether said first quality of service isacceptable; responsive to said determining, offering by said first oneof said pair to permit one of joining in coordination with said secondone of said pair and not joining in coordination with said second ofsaid pair; responsive to said offering by said first one of said pair topermit joining in coordination with said second one of said pair,requesting by said second one of said pair a second indicator indicatinga second quality of service acceptable to said first one of said pair;responding by said first one of said pair with said second indicator;receiving by said second one of said pair said second indicator;responsive to said second indicator, determining by said second one ofsaid pair to permit joining in coordination with said first one of saidpair; and responsive to determining by said second one of said pair topermit joining in coordination with said first one of said pair,determining a quality of service provision for said coordination.
 2. Amethod as claimed in claim 1, further comprising the step of having saidfirst one of said pair comprise a resource component and said second oneof said pair comprise a coordinator.
 3. A method as claimed in claim 2,further comprising the step of having said resource component comprise aresource manager.
 4. A method as claimed in claim 2, further comprisingthe step of having said resource component comprise a resource adapter.5. A method as claimed in claim 3, further comprising the step of havingsaid resource manager comprise a database manager.
 6. A method asclaimed in claim 3, further comprising the step of having said resourcemanager comprise an Enterprise Resource planning system.
 7. A method asclaimed in claim 2, further comprising the step of having saidcoordinator comprise a transaction manager.
 8. A method as claimed inclaim 1, further comprising the step of having said first one of saidpair comprise a coordinator and said second one of said pair comprise aresource component.
 9. A method as claimed in claim 8, furthercomprising the step of having said resource component comprise aresource manager.
 10. A method as claimed in claim 8, further comprisingthe step of having said resource component comprise a resource adapter.11. A method as claimed in claim 9, further comprising the step ofhaving said resource manager comprise a database manager.
 12. A methodas claimed in claim 9, further comprising the step of having saidresource manager comprise an Enterprise Resource planning system.
 13. Amethod as claimed in claim 1, further comprising the step of performingthe previous steps at startup of a server.
 14. A method as claimed inclaim 13, further comprising the step of: sending, by said server, arequest to a first one of a resource and coordinator pair to initiaterequesting said first indicator indicating a quality of servicesupported by a second one of resource and coordinator pairs.
 15. Amethod as claimed in claim 1, further comprising the step of having atleast one of said first and second qualities of service comprise acommit phase support.
 16. A method as claimed in claim 15, furthercomprising the step of having said commit phase support comprise atleast one of one phase commit support and two phase commit support. 17.A method as claimed in claim 1, further comprising the step of having atleast one of said first and second qualities of service compriserecovery support.
 18. A method as claimed in claim 1, further comprisingthe step of having at least one of said resource component andcoordinator pair comprise a platform-independent program code component.19. A method as claimed in claim 1, further comprising the step ofrenegotiating a quality of service provision.
 20. A computer programproduct comprising computer program code tangibly embodied in a computerreadable medium, said computer program code comprising instruction to,when provided to a computer system and executed, cause said computer toperform the steps of: requesting by a first one of a resource componentand coordinator pair a first indicator indicating a first quality ofservice supported by a second one of said pair, said first one and saidsecond one of said pair disposed within different heterogeneousprocessing systems; responding by said second one of said pair with saidfirst indicator; receiving by said first one of said pair said firstindicator; responsive to said first indicator, determining by said firstone of said pair whether said first quality of service is acceptable;responsive to said determining, offering by said first one of said pairto permit one of joining in coordination with said second one of saidpair and not joining in coordination with said second of said pair;responsive to said offering by said first one of said pair to permitjoining in coordination with said second one of said pair, requesting bysaid second one of said pair a second indicator indicating a secondquality of service acceptable to said first one of said pair; respondingby said first one of said pair with said second indicator; receiving bysaid second one of said pair said second indicator; responsive to saidsecond indicator, determining by said second one of said pair to permitjoining in coordination with said first one of said pair; and responsiveto determining by said second one of said pair to permit joining incoordination with said first one of said pair, determining a quality ofservice provision for said coordination.
 21. A computer program productas claimed in claim 20, further comprising the step of having said firstone of said pair comprise a resource component and said second one ofsaid pair comprise a coordinator.
 22. A computer program product asclaimed in claim 21, further comprising the step of having said resourcecomponent comprise a resource manager.
 23. A computer program product asclaimed in claim 21, further comprising the step of having said resourcecomponent comprise a resource adapter.
 24. A computer program product asclaimed in claim 22, further comprising the step of having said resourcemanager comprise a database manager.
 25. A computer program product asclaimed in claim 22, further comprising the step of having said resourcemanager comprise an Enterprise Resource planning system.
 26. A computerprogram product as claimed in claim 21, further comprising the step ofhaving said coordinator comprise a transaction manager.
 27. A computerprogram product as claimed in claim 20, further comprising the step ofhaving said first one of said pair comprise a coordinator and saidsecond one of said pair comprise a resource component.
 28. A computerprogram product as claimed in claim 27, further comprising the step ofhaving said resource component comprise a resource manager.
 29. Acomputer program product as claimed in claim 27, further comprising thestep of having said resource component comprise a resource adapter. 30.A computer program product as claimed in claim 28, further comprisingthe step of having said resource manager comprise a database manager.31. A computer program product as claimed in claim 28, furthercomprising the step of having said resource manager comprise anEnterprise Resource planning system.
 32. A computer program product asclaimed in claim 20, further comprising the step of having the computerprogram code being executed at startup of a server.
 33. A computerprogram product as claimed in claim 20, further comprising instructionsto, when loaded into a computer system and executed, cause said computerto perform the step of: sending, by said server, a request to a firstone of a resource and coordinator pair to initiate requesting said firstindicator indicating a quality of service supported by a second ofresource and coordinator pairs.
 34. A computer program product asclaimed in claim 20, further comprising the step of having at least oneof said first and second qualities of service comprise a commit phasesupport.
 35. A computer program product as claimed in claim 34, furthercomprising the step of having said commit phase support comprise atleast one of one phase commit support and two phase commit support. 36.A computer program product as claimed in claim 20, further comprisingthe step of having at least one of said first and second qualities ofservice comprise recovery support.
 37. A computer program product asclaimed in claim 20, further comprising the step of having at least oneof said resource component and coordinator pair comprise aplatform-independent program code component.
 38. A computer programproduct as claimed in claim 20, further comprising the step ofrenegotiating a quality of service provision.
 39. Apparatus forintegrating heterogeneous processing systems, said apparatus comprising:a first requestor for requesting by a first one of a resource componentand coordinator pair a first indicator indicating a first quality ofservice supported by a second one of said pair, said first one and saidsecond one of said pair disposed within different heterogeneousprocessing systems; a first responder for responding by said second oneof said pair with said first indicator; a receiver for receiving by saidfirst one of said pair said first indicator; a determining element beingresponsive to said first indicator, for determining by said first one ofsaid pair whether said first quality of service is acceptable; anoffering element being responsive to said determining, for offering bysaid first one of said pair to permit one of joining in coordinationwith said second one of said pair and not joining in coordination withsaid second of said pair; a second requestor being responsive to saidoffering by said first one of said pair to permit joining incoordination with said second one of said pair, for requesting by saidsecond one of said pair a second indicator indicating a second qualityof service acceptable to said first one of said pair; a second responderfor responding by said first one of said pair with said secondindicator; a second receiver for receiving by said second one of saidpair said second indicator; a second determining element beingresponsive to said second indicator, for determining by said second oneof said pair to permit joining in coordination with said first one ofsaid pair; and a third determining element being responsive todetermining by said second one of said pair to permit joining incoordination with said first one of said pair, for determining a qualityof service provision for said coordination; wherein the apparatusutilizes a processor to integrate the heterogeneous processing systems.40. Apparatus as claimed in claim 39, wherein said first one of saidpair comprises a resource component and said second one of said paircomprises a coordinator.
 41. Apparatus as claimed in claim 40, whereinsaid resource component comprises a resource manager.
 42. Apparatus asclaimed in claim 40, wherein said resource component comprises aresource adapter.
 43. Apparatus as claimed in claim 41, wherein saidresource manager comprises a database manager.
 44. Apparatus as claimedin claim 41, wherein said resource manager comprises an EnterpriseResource planning system.
 45. Apparatus as claimed in claim 40, whereinsaid coordinator comprises a transaction manager.
 46. Apparatus asclaimed in claim 39, wherein said first one of said pair comprises acoordinator and said second one of said pair comprises a resourcecomponent.
 47. Apparatus as claimed in claim 46, wherein said resourcecomponent comprises a resource manager.
 48. Apparatus as claimed inclaim 46 wherein said resource component comprises a resource adapter.49. Apparatus as claimed in claim 47, wherein said resource managercomprises a database manager.
 50. Apparatus as claimed in claim 47,wherein said resource manager comprises an Enterprise Resource planningsystem.
 51. Apparatus as claimed in claim 50, further comprising thestep of: sending, by said server, a request to a first one of a resourceand coordinator pair to initiate requesting said first indicatorindicating a quality of service supported by a second one of resourceand coordinator pairs.
 52. Apparatus as claimed in claim 39, wherein atleast one of said first and second qualities of service comprises acommit phase support.
 53. Apparatus as claimed in claim 52, wherein saidcommit phase support comprises at least one of one phase commit supportand two phase commit support.
 54. Apparatus as claimed in claim 39,wherein at least one of said first and second qualities of servicecomprises recovery support.
 55. Apparatus as claimed in claim 39,wherein at least one of said resource component and coordinator paircomprises a platform-independent program code component.
 56. Apparatusas claimed in claim 39, further comprising the step of renegotiating aquality of service provision.